Refresh Bricks fonts dropdown on mount via REST endpoint - #231

plugins/SLASHED-for-WP/integrations/bricks/admin-app/src/lib/api.js (1)

96-99: ⚡ Quick win

Normalize the REST payload shape before returning.

Line 98 currently returns data.fonts ?? []; a non-array value can still leak through and break downstream .some/.find/.length usage. Coerce to an array at the boundary.

Proposed patch

 export async function fetchBricksFonts() {
   const { url, nonce } = meta.rest;
   if (!url) {
     console.info('[slashed-admin] (dev) would GET /bricks-fonts');
-    return meta.bricksFonts;
+    return Array.isArray(meta.bricksFonts) ? meta.bricksFonts : [];
   }
   const res = await fetch(url + '/bricks-fonts', {
     credentials: 'same-origin',
     headers: { 'X-WP-Nonce': nonce },
   });
   if (!res.ok) throw new Error(await res.text() || `HTTP ${res.status}`);
   const data = await res.json();
-  return data.fonts ?? [];
+  return Array.isArray(data?.fonts) ? data.fonts : [];
 }

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@plugins/SLASHED-for-WP/integrations/bricks/admin-app/src/lib/api.js` around
lines 96 - 99, Normalize the REST payload by coercing data.fonts into an array
before returning: in the block that currently does `const data = await
res.json(); return data.fonts ?? [];`, replace that return with logic that
checks data.fonts and returns an array — e.g., if Array.isArray(data.fonts)
return it, if it's a single truthy item wrap it as [data.fonts], otherwise
return [] — so downstream callers using .some/.find/.length always get an array.

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes